home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Diamond Collection
/
The Diamond Collection (Software Vault)(Digital Impact).ISO
/
cdr05
/
womenu33.zip
/
WOMENU.DOC
< prev
next >
Wrap
Text File
|
1995-03-17
|
53KB
|
1,264 lines
WOmenu
══════
The Windows Office Menu
▄▄▄▄▄▄▄▄▄▄▄
█ ▄▄▄▄▄ █ (C)Copyright 1994-1995
█ █ █ █
█ ▀▀▀▀▀ ▀ Bremer Corporation
█ ▄▄▄▄▄ ▄ Austin, Texas
█ █ █ █
█ ▀▀▀▀▀ █ All rights reserved
▀▀▀▀▀▀▀▀▀▀▀
FTP ftp://io.com/pub/usr/zboray/shareware
WWW http://www.io.com/~zboray/shareware
Version 3.3a
March 1995
TABLE OF CONTENTS
══════════════════════════════════════════════════════════════════════════════
Topic Section
Introduction ...................................................... 3
Miscellaneous ..................................................... 4
Quick Start ....................................................... 6
Upgrade and Registration Procedures ............................... 7
Upgrade Procedures
Registration Procedures
Commands .......................................................... 8
Menu Modes ........................................................ 9
Setup Mode
User Mode
WOmenu Setup ...................................................... 10
Setup
Menus
Sub-menu Titles
Notes
Menu Rights ....................................................... 12
Notes
Menu Icons ........................................................ 19
Users Windows Environment.......................................... 20
DOS Environment Variables ......................................... 21
DOS Program PIF Files ............................................. 22
Software Metering Service ......................................... 23
WOmeter Windows Metering Utility .................................. 24
DOSmenu Menu System ............................................... 25
Shareware ......................................................... 26
INTRODUCTION
══════════════════════════════════════════════════════════════════════════════
WOmenu was designed as a simple yet powerful menu system for both network and
stand-alone environments where users must operate under Windows(tm). Our
environment demands a safe, secure menu to help our users run both DOS and
Windows applications without allowing undo access to our large Texas-wide
NetWare network. The menu system we needed had to be both easy to use and
flexible and yet it had to stay out of the way as much as possible for our
user operations. Because we could not find one, we wrote our own. We hope it
helps you control your Windows environment as well. Please use WOmenu as you
see fit, but if you continue to use it, you should register according to the
SHAREWARE section below.
Here is an example of why you might need WOmenu to help you:
You have a network with one or more servers and many users. Most of these
users run a couple of business-specific apps and some utilities that you
allow. Now, you are finding that these users can be much more productive if
they could run their one or two business apps at the same time while having
their email and a utility or two instantly available. This, of course, means
multi-tasking, which probably means Windows. But how do you keep all of those
'nice' things that Windows offers, like the File Manager and Games away from
the users while defining a Program Group that makes sense to _each_ user?
Enter WOmenu...it was made to solve just that!
Here is a quick overview of WOmenu:
o Knows NetWare operating systems.
o Flexible user-specific menus.
o Unlimited menu items.
o Unlimited sub-menus.
o Run any program, DOS or Windows based.
o Prevent multiple runs of the same program.
o Easily operate the menu system without having to outfit users with mice.
o Many rights options to determine whether a menu item is usable by a user.
o Works great with NetWare and any other network operating systems. Also
works well as a stand-alone system.
o Complete user logging capabilities.
o Complete Software Metering Services for applications run through WOmenu.
o Works well in conjunction with our DOS-based network system, DOSmenu.
MISCELLANEOUS
══════════════════════════════════════════════════════════════════════════════
Requirements
────────────
WOmenu's only additional requirement is that it needs the Visual Basic 3.0
runtime library, VBRUN300.DLL, in order to run. If you do not have this file
yet, it may be downloaded from almost any on-line service. We can also
provide you with this program, if required (it is shipped with the registered
package).
Startup Options
───────────────
WOmenu is normally started by specifying the program file as the Windows
shell. The first line in your SYSTEM.INI should read
shell=[path]womenu.exe
However, it may be started directly from within Windows. In this case, the
command should be
[path]womenu.exe
Here, quitting WOmenu will not quit Windows.
Required Files
──────────────
The following files are necessary to run WOmenu:
WOMENU.EXE The WOmenu program.
WOMENU.INI The WOmenu INI (menu) file (see WOMENU SETUP section below).
MLIST.VBX A Visual Basic library file for WOmenu.
VBCTL3D.VBX Another Visual Basic library file for WOmenu.
CMDIALOG.VBX Yet another Visual Basic library file for WOmenu.
COMMDLG.DLL A Windows support file.
NWNETAPI.DLL A Windows NetWare support file (needed when running on NetWare)
VBRUN300.DLL The main Visual Basic runtime library.
Optional Files
──────────────
WOUSER.INI This file holds user-specific options and is stored in the
user's private Windows directory.
WOMENU.LOG (You choose name) If logging is enabled, this file is appended
every time a user performs a menu action. Included statistics
are: user name, node address, server name, date, time, and
menu action.
WOMENU.MTR (You choose name) If metering is enabled, this is the central
file where the software metering information is kept.
WOCALC.EXE A calculator utility that works with the keyboard as well as a
mouse (registered version only).
WOCAL.EXE A calendar utility that easily works with the keyboard as well
as a mouse (registered version only).
WOVIEW.EXE A file viewer with a simple interface that works with the
keyboard as well as a mouse (registered version only).
WOMETER.EXE A Windows real-time Software Meter Viewer/Reset utility.
QUICK START
══════════════════════════════════════════════════════════════════════════════
To quickly get the menu system up and running, do the following (check the
documentation later for specifics):
o Copy all WOmenu files to your main Windows directory. This directory is
normally C:\WINDOWS on a stand-alone system and F:\WINDOWS on a network
system. To use WOmenu for all of your users, copy it to the Windows
network directory. (The installation SETUP program should do this step
for you, but you may need to check that it really went to your network
shared Windows and not your local.)
o VBRUN300.DLL must also be in the \WINDOWS. (Installation SETUP will do
this also for registered installations.)
o If not already running Windows, run it.
o Run 'WOMENU.EXE' from the Windows directory. This first run will make a
default WOMENU.INI file in the same Windows directory.
That's all there is to it. You now have an operating menu system. You may
use WOmenu in the Setup Mode to change your menu items and sub-menus as you
desire. After you get the menu the way you want it (especially if you
administer a network) you will want to change some of the default setup
options in the INI file and add appropriate rights to the menu item lines so
as to lock your users and protect your network. This is accomplished with
the Setup command. See the WOMENU SETUP below for help in this area.
If you plan to run in a network multi-user environment, then check these
sections out also: DOS PROGRAM PIF FILES and USERS WINDOWS ENVIRONMENT.
Registered users need to perform the registtation procedure once as outlined
in the UPGRADE AND REGISTRATION PROCEDURES section which follows.
UPGRADE AND REGISTRATION PROCEDURES
══════════════════════════════════════════════════════════════════════════════
UPGRADE PROCEDURES
══════════════════
There are two ways to upgrade your registered version of WOmenu.
Download from the Internet with Anonymous FTP
─────────────────────────────────────────────
You may download the latest shareware ZIP file (WOMENU??.ZIP) at any time,
expand it, and then install its files over your existing registered
files during installation. You may then need to follow the registration
instructions for registering your product as originally accomplished when you
bought the product. For those who own version prior to 3.3, call Bremer
Corporation for a registration number. You are guaranteed free upgrades in
this manner for at least two minor updates of the product. For Internet
file sites, see the cover page of this manual.
By mail directly from us
────────────────────────
You may call or write to us and request the latest registered update. Upgrade
costs are $50 US for network versions and $25 US for single-user versions
(both prices include shipping and handling). This again guarantees you at
least two more minor update upgrades.
REGISTRATION PROCEDURES
═══════════════════════
To register your product, perform the following steps after installation:
1. Run WOmenu.
2. Press the "Register" button on the initial shareware screen.
3. Enter your registration number on the Register line.
4. Press Enter.
You will find your registration number on the Software License letter that was
shipped to you along with your product.
You should only have to perform this procedure once. However, if you upgrade
the product at a later date with a newer version obtained from an online
service or bulletin board service, you may need to perform this procedure
again.
Therefore, you should keep your registration number in a safe place. Your
name and registration number is also kept on file at Bremer Corporation.
Please contact Bremer Corporation if you have problems with this procedure.
COMMANDS
══════════════════════════════════════════════════════════════════════════════
SETUP Provides for complete menu system parameter setup for the
administrator. (Users never see this command.)
EDIT Allows editing of the highlighted menu item or sub-menu item. Edit
fills in all parts of a menu item or sub-menu item except for the
item's menu rights. See MENU RIGHTS section below. (Users never
see this command.)
MOVE Allows moving of the highlighted menu item or sub-menu item within
the same menu. (Users never see this command.)
INSERT Allows the insertion of a new menu item or sub-menu item. (Users
never see this command.)
DELETE Allows the deletion of the highlighted menu item or sub-menu item.
(Users never see this command.)
HELP Brings up a context sensitive help screen.
QUIT Quits the menu system. If WOmenu was used as the Windows shell, it
will first check that all programs have been quit and then it will
quit Windows as well.
F2 Toggles the Setup/User Modes. This command can (and should be) be
password-protected. It is useful when the system is in User Mode
and the administrator needs to change the menu and/or system.
(Users never see this command.)
F4 Quickly accesses the user note screen for editing when in Setup
Mode. (Users never see this command.)
F5 Refreshes (rereads) the INI file which contains the actual menu.
(Users never see this command.)
SHIFT+DEL Copy the highlighted menu item to the WOmenu copy buffer and then
delete the highlighted menu item from the current menu (Ctrl+X).
CTRL+INS Copy the highlighted menu item to the WOmenu copy buffer (Ctrl+C).
SHIFT+INS Insert the WOmenu copy buffer into the current menu (Ctrl+V).
MENU MODES
══════════════════════════════════════════════════════════════════════════════
WOmenu comes in two flavors - Setup Mode and User Mode.
SETUP MODE
══════════
Setup mode is the default after installing Womenu. This is a convenience item
that allows you full editing rights to the menu system. In this mode you will
be able to:
o Select the default menu startup mode for your users.
o Setup all network options.
o Setup activity logging.
o Setup software metering.
o Setup all menu interface options.
o Define startup programs and their 'rights'.
o Edit the user note window (also with F4 from menu window).
o Edit the optional user help screen.
o Select a menu font.
While viewing the menu window, you will see all menu items, even if you do not
have rights to them. Those for which you do not have rights are shown in red.
When finished with your setup, and before allowing users into WOmenu, you
should change the default mode to user Mode to protect your network
environment.
USER MODE
═════════
This is the normal operating mode for WOmenu. In this mode, all menu rights
are honored and users only see what their rights allow them to see.
Also, the only help screen they see is the default user help screen, unless
you opt to make a new one for them.
Users will have up to three commands on their menu window:
Help - the user help screen (default or defined by you in setup).
Out - If activated by you, then users may use this command to activate
their personal on-demand password-protected screen saver. If not
activated for users, this command will not be shown.
Note - If you have left them a note, then this command will allow them
to view it again whenever they wish (during the dates you have set
for the note). if there is no note, or if the user has no rights
to the note, this command will not be shown.
Quit - Allows users to quit the menu system (and Windows if WOmenu is
their shell -which it should be). Additionally, this command
changes to "Back" when a user opens a sub-menu thereby leaving the
main menu.
WOMENU SETUP
══════════════════════════════════════════════════════════════════════════════
WOmenu has one overall setup command that leads to the entire menu setup
functions. All setup options are stored in the main INI file (which is also
the actual menu file). This section explains the different Setup options.
SETUP
═════
User Mode
─────────
This is the normal default startup menu mode for users. In this mode, users
can only run the menu items that you determine through menu rights (discussed
below). They never see any setup functions or setup help screens. Once you
have finished with your preliminary setup chores, set this mode as the
default.
Setup Mode
──────────
This mode is for initial setup chores. Initially, Womenu is set to start in
this mode for ease of setup. Once you have finished preliminary setup chores,
and definitely before you allow users to use the menu, change the default mode
to User Mode. As an administrator, you may always return to this mode by
simply presing F2 and entering the admin password (see below). Setup mode has
various help screens to guide you in setting up the menu properly for your
users.
Setup Password
───────────────
Place a password here to inhibit the F2 Setup/User Mode command toggle, which
is useful for the administrator to have access to changing the menu even if it
is in User Mode. (This answer is scrambled within the INI file.)
Attempt To Use NetWare
──────────────────────
This switch determines whether WOmenu tries to access the NWNETAPI.DLL to
accomplish NetWare tasks (such as getting the user name and looking for groups
that the user belongs to). Set this to NO if not on NetWare so WOmenu will
not issue error messages on startup.
User Var
────────
Here you determine whether you want NetWare or a login script DOS variable to
determine the active user. If on NetWare, use NetWare. If not on NetWare,
or if you develop problems with returned values from NetWare 4.x, use the DOs
variable approach.
If using DOS variables, they should be set in the main login script. See DOS
ENVIRONMENT VARIABLES section below for how to define this variable.
This function is only required if you plan to use the User right (see MENU
RIGHTS section below).
Server Var
──────────
Here you determine whether you want NetWare or a login script DOS variable to
determine the user's home server. If on NetWare, use NetWare. If not on
NetWare, or if you develop problems with returned values from NetWare 4.x, use
the DOs variable approach.
If using DOS variables, they should be set in the main login script. See DOS
ENVIRONMENT VARIABLES section below for how to define this variable.
This function is only required if you plan to use the Server right (see MENU
RIGHTS section below).
Keep in mind that WOmenu should be run from the actual server that defines the
user's groups.
Node Var
────────
Here you determine whether you want NetWare or a login script DOS variable to
determine the user's workstation node address. If on NetWare, use NetWare.
If not on NetWare, or if you develop problems with returned values from
NetWare 4.x, use the DOS variable approach.
If using DOS variables, they should be set in the main login script. See DOS
ENVIRONMENT VARIABLES section below for how to define this variable.
This function is only required if you plan to use the Node right (see MENU
RIGHTS section below).
Groups
──────
Here you decide whether you will activate the group right function. For all
NetWare 2.x and 3.x servers, this function works correctly. It will only work
correctly on 4.x if bindery emulation is turned on.
NOTE: In each case aboce, the "Results" box will help you to decide if your
environment will work with the appropriate switch. On NetWare 2.x and 3.x,
all functions should work fine.
Logging
───────
This is used to activate user activity logging.
Log File
────────
The name of the log file to use, like Log File=f:\share\womenu.log. Users
must have 'write' access to this file in order for logging to work on a
network. The log function logs menu start, menu end, and all program starts.
The user's login name (if defined), server (if defined), node address (if
defined), date, and time name are all entered into the log file. You may wish
to periodically erase or archive this file because it can get quite large
after a while if you have many users.
Metering
────────
This is used to activate software metering.
Meter File
──────────
The name of the meter file to use, like MeterFile=f:\share\womenu.mtr. Users
must have 'write' and 'erase' access to this file in order for metering to
work on a network. See SOFTWARE METERING SERVICE section below for specifics
on software metering.
Main Menu Title
───────────────
This simply determines the title of the first, main menu window.
Message
───────
If filled in, this message will be displayed unobtrusively at the bottom of the users' menu
window (It does not show while in Setup Mode). WOmenu looks for this text in
the INI file every time the user changes window focus or runs an item. So you
may change it on the fly and know that users will soon see it.
Allow "Out" Message Function
────────────────────────────
This determines whether uses will be able to access the Out message function.
This function is an on-demand screen saver with a user-determined message.
They should use it when they will be away from their desk for any period of
time to help protect their desktop.
NOTE: For this function to be truly effective, you should turn off the
Windows Task Manager in the users' WIN.INI files. Under some Windows
circumstances, this involves actually removing the file TASKMAN.EXE from the
users' path and from the main Windows directory (Other non-menu users may
still use it by adding the path to the file to their WIN.INI file).
Use NetWare Unencrypted Passwords
─────────────────────────────────
For the Out message function above. On NetWare, with ALLOW UNENCRYPTED
PASSWORDS=ON (set at the file server), users will conveniently be able to use
their NetWare password for their Out screen saver. Otherwise, WOmenu will
bring up dialog boxes to let them define their own (and this password will be
saved encrypted to their private WOUSER.INI file).
NOTE: In either password case above, you as the administrator will be able to
"get in" to a user's desktop, if necessary, by issuing the overall admin
password that you defined for the Setup Mode entry.
Save Menu Window Position
─────────────────────────
You may move and resize the menu window while in Setup Mode to any startup
position you wish for your users. Use this to save that position.
Reset Window Position And Font
──────────────────────────────
If you get into trouble with the Window positioning or menu font changes, use
this to reset them.
Startup
───────
Here you may add programs that should start automatically when the menu system
starts for a user. These programs can have menu rights that will determine
for which users they will start as well. This is an expanded substitute for
the Windows Startup Group. WOmenu still honors any programs defined on the
load= and run= lines of each user's private WIN.INI file.
NOTE: The programs you define here will only start when and if the menu
system was started in the User Mode and WOmenu was defined as the Windows
shell for the user.
Note
────
This is where you may define a note that will be seen by each user starting
the menu system. You may also access this function from the menu window with
F4 when in Setup Mode. While editing the note text, press Shift+Enter to
enter a new line. The note window's size and position is saved as well. The
note will only show between the dates that you enter. This makes it
convenient in that you do not have to remember to turn a note "off". The note
will also only show if the user has rights to the rights definition that you
can optionally enter.
WOmenu holds a variable for each user to tell whether the note has been
changed and let's the user's environment know whether it should re-display the
note. Therefore you can change the note on the fly and your users will soon
see it, even if they are already in WOmenu.
User
────
This is where the optional alternate help screen for users is defined. While
editing the user help text, press Shift+Enter to enter a new line. As with
the note, the window size and position is saved as well.
Font
────
The menu font. Be careful not ot make it too large. Be sure all of your
users have access to the font in their WINI.INI files!
MENUS
═════
The following is offered to give you, as the administrator knowledge of the
menu portion of the WOMENU.INI file. Whenever possible, you should only make
changes to this file through WOmenu itself. However, if something goes awry,
this will allow you to fix the problem.
[sub-menu titles]
─────────────────
These section headings define the sub-menus used in the menu system with the
exception of the first one which is always labeled [Main menu]. The following
sections, in fact, define the names of any and all sub-menus.
Pgm#= {Pgm1, Pgm2, Pgm3, etc.}
─────
These entries hold all information for each menu item or sub-menu item. The
numbers define only the order of items on the menu. In User Mode, only
the items that pass the 'rights' tests will be actually be shown.
The information is separated by commas, so DO NOT use commas in your
descriptions. Here are the sections:
Title, Window Title, Description, Program, Workdir, Icon File, Icon #, Rights
Title
─────
The item's button text, like '&WordPerfect'. Use the & character to
underscore a letter for a hotkey, if desired. For sub-menus, do not add the
< or > to the title; WOmenu will handle this.
Window Title
────────────
IMPORTANT: The actual name of the program's Windows title. You may have to
run a program it check this one time. Do not add any dynamically appended
text here. For instance, Notepad's Windows title in version 3.1 is 'Notepad'.
But after loading a program, it becomes 'Notepad - [filename]'. Make sure
only to add the 'Notepad' part here. Case is not significant. Another
example: for Winword, use 'Microsoft Word'. For PIF files, you will decide
yourself what that Windows title will be -- just place it here as well -- and
be sure they are unique from any other program's Windows titles that may be
run from the menu.
Description
───────────
The item's optional description text, like 'A word processor'.
Program
───────
The item's executable call to Windows and/or DOS, like 'f:\apps\wp\wp.exe'.
This could be a PIF file or batch file as well.
Workdir
───────
The item's optional work directory, like 'h:\'.
Icon File
─────────
The file used by Womenu to extract the menu item icon.
Icon #
──────
The number of the icon in the Icon File.
Rights
──────
The item's optional rights to determine whether the user will get this item on
their menu, like '{d=f:\apps\wp}'. See the MENU RIGHTS section for specifics
on this powerful feature.
SUB-MENU TITLES
═══════════════
Sub-menu titles are annotated slightly differently than normal menu items.
Where '&WordPerfect' may define a menu item, '< &Word Processing >' would
define a sub-menu (and subsequent new section '[Word Processing]'). WOmenu
takes care of this for you, but if you decide to edit your menu file manually,
take this into consideration. We strongly suggest that you DO NOT edit the
INI file yourself -- use the Setup Mode commands to accomplish this.
NOTES
═════
Not all sections must be filled out. Although the title and program section
are always required for a menu item, only the title section is required for a
sub-menu item. If you must edit the INI file yourself, be sure that commas
remain to identify which section text belongs to, like:
;─────
Pgm1=&Lotus 1-2-3,LOTUS 1-2-3,,123
;─────
This is enough to run 123 if it exists and can be found in the path.
MENU RIGHTS
══════════════════════════════════════════════════════════════════════════════
A powerful means of segregating the menu file between users is by applying the
'rights' feature in User Mode. You can decide what items should actually
appear on a user's menu by defining certain rights for some or all of the
items listed in the INI file. You add these rights into the menu file with
the Edit or Insert commands while in Setup Mode. Let's discuss each right.
NOTE: While in Setup Mode, you will always see all of the menu items, whether
you, even as an administrator, have the rights for an item or not. For
example, if a menu item has a directory right of {d=h:\} and you do not have a
mapped H drive, then you actually do not have rights to that item. While in
Setup Mode, this item will appear red on the menu screen as a reminder that
that item is not available in your current network state.
All rights assumed
─────────────────-
Right = no rights entered. This method is the quickest and least secure way
of checking users' rights because it checks nothing. In other words, a menu
item will show up on a user's menu, period. Here, you will be relying on your
defined network rights to determine whether a user will be able to _run_ an
item or not (they will see them on their menu).
;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, h:\,,,
;─────
User gets item if it is available, period, because the final section is empty.
Group rights
────────────
Right = {g=NetWare group name or g=NetWare group name1, group name2 ..}.
WOmenu will look to see if any of the listed groups are part of the groups
the user is a member of when it reads the menu file, and if the user is a
member of none of them, it will not place the item on the user's menu.
This right only works on NetWare 2.x and 3.x and NetWare 4.x if bindery
emulation is enabled.
;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, h:\,,, {g=everyone}
;─────
User gets item only if the user is a member of EVERYONE.
Directory rights
────────────────
Right = {d=directory name or d=directory name1,directory name2 ..}. WOmenu
will look to see if any of the listed directories exist when it reads the menu
file, and if none of them do, it will not place the item on the user's menu.
;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, h:\,,, {d=f:\apps\editor}
;─────
User gets item only if F:\APPS\EDITOR is 'visible' in the user's environment.
Group rights (how to 'fake' this right on non-NetWare servers)
────────────
Right = --there is no such right--; use directory rights instead. WOmenu was
built to be generic as far as networks are concerned. Therefore, the networks
'groups' are not used. Instead, we use a foolproof method that actually
invokes the directory right method.
Let's say you only want users who are a member of group WP or a member of
group WORD_PROCESS to be able to run WordPerfect. Within SYSCON or NETCON
(for large NetWare networks), you should give each of these groups a trustee
right assignment to a directory, like F:\FLAGS\WP in this case. Read/file
scan network rights are normally enough to 'see' the directory.
Then, in the user's INI (menu) file, define the following right:
Pgm1=&WordPerfect, WORDPERFECT FOR WINDOWS, A wordprocessor, ...
... f:\apps\wp\wp, h:\,,, {d=f:\flags\wp}
which in effect will perform the same function as checking for a member of a
group, because only those users who _are_ a member of the actual group in
question will be able to see this directory. You could probably use
{d=f:\apps\wp} here as well.
Another example: for members of the ACCOUNTING group...
Pgm1=&Accounting package, GREAT PLAINS, Great Plains Accounting, ...
... f:\apps\gp\great.exe, h:\,,, {d=f:\flags\gp}
or you could probably use {d=f:\apps\gp} here.
File rights
───────────
Right = {f=file name or f=file name1,file name2 ..}. WOmenu will look to see
if any of the listed files exist for the user when it reads the menu file, and
if none of them do, it will not place the item on the user's menu.
;─────
Pgm1=&Notepad, NOTEPAD, Win Notepad, notepad, h:\,,, {f=f:\windows\notepad.exe}
;─────
User gets item only if F:\WINDOWS\NOTEPAD.EXE is 'visible' in the user's
environment.
User rights (uses User Var definition)
───────────
Right = {u=user_id or u=user_id1,user_id2 ..}. This method takes the
discrimination down to the actual user id running the system. If the user
name is in the list, then the user gets the item on their menu (if any other
specified rights are also approved).
;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, h:\,,, {u=joeb}
;─────
User gets item only if his user logon ID is JOEB.
Server rights (uses Server Var definition)
─────────────
Right = {s=server_name1 or s=server_name1,server_name2 ..}. Here, by placing
one or more server names with a menu item, you are saying only show this item
when the user is logged into one of those servers. Remember that if using
NetWare to determine the user's server, WOmenu must be started from that
server.
;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, h:\,,, {s=main_server}
;─────
User gets item only if the user is logged into and running on MAIN_SERVER.
Node rights (uses Node Var definition)
───────────
Right = {n=node_address or n=node_address1, node_address2 ..}. This method
takes the discrimination down to the actual user's workstation. If the node
address is the same as that of the workstation, then the user gets the item
on their menu (if any other specified rights are also approved).
;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, h:\,,, {n=fa164505}
;─────
User gets item only if his/her workstation's address is FA164505.
Environment rights
──────────────────
Right = {e=dos_env_var~env_var_text, ..}. This powerful right tests for the
contents of any DOS variable. For instance, to run a menu item depending on
what room a person is in, set ROOM=room_number at login; then enter this right
for the menu item in the menu file: {e=room~102} to test for room 102.
;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, h:\,,, {e=room~102}
;─────
Map rights (not really a 'right')
──────────
Right = {a=drive_letter~server/volume:directory} (up to 3 maps - {}{}{}).
On NetWare, to run a program that requires specific directory structures,
you can use this right to map the user's drive_letter to this right's
server/volume:directory. This will happen just before the user runs the
program. This is not a restrictive right: it will not prevent the menu item
from showing up on the user's menu. it is a run right that facilitates the
running of the program.
Mapping notes:
o This right only works on NetWare environments.
o The user should have been automatically attached to the server in
question in the NetWare login script (if not, the user will be asked for
their password to the server).
o The drive in question, should it already contain a mapping, will lose
that mapping for this new mapping (do not map to critical map drives).
o The mapping is permanent for the user's Windows session (unless remapped
again later).
o This right is only effective with Windows-based programs. For DOS-based
programs, perform your mapping statements in the batch file that actually
runs the program.
o To map more than one drive at once (up to three), present the rights in
their own separate sets, like: {}{}{}.
;─────
Pgm1=&OurPgm, OUR PROGRAM, Our Main App, g:\apps\ourpgm, h:\,,, ...
... {a=g~acctg/sys:\apps}
;─────
Drive G will be mapped on server ACCTG, volume SYS to the \APPS directory.
Software metering rights (not really a 'right')
────────────────────────
Right = {m=command[:number]}. Entering this rule on an item's right line will
force the command for the item to be metered, if metering is turned on and the
meter file has been defined (within WOMENU.INI). Please see the SOFTWARE
METERING SERVICE section for a complete discussion of this capability.
;─────
Pgm1=&Word, MICROSOFT WORD, Microsoft Word, winword.exe, h:\,,, {m=winword:25}
;─────
This item will run as long as less than 25 other users are running it.
Password rights (not really a 'right')
───────────────
Right = {p=password where password is any alphanumeric, non-case sensitive,
phrase}. Placing a password on a menu item means that when the user selects
this item, the user will be prompted for the correct password. (This right is
scrambled within the INI file).
;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, h:\,,, {p=restrict}
;─────
User gets item only if he or she can answer the password prompt with RESTRICT.
Question rights (not really a 'right')
───────────────
Right = {q=your question that demands a yes/no answer?} This method simply
pops up a question and asks for a Yes or No answer. If no, it will not run.
;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, h:\,,, {q=Are you sure?}
;─────
Will only run if the user answers Yes.
NOTES
═════
More than one of the above methods may be used at one time, either within the
same right grouping or by having two or more groupings. For example, you can
place both a server (s=) and a group (u=) method on the same menu item, like:
;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad,,, {u=joeb}{s=server1}
;─────
Here, it is read as user joeb _AND_ on server1.
or by using the OR ';' such as
;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad,,, {u=joeb;s=server1}
;─────
Here, it is read as user joeb _OR_ on server1.
Note that when using more than one grouping {}, each of the groupings must be
true for the item to be shown (they are ANDed). When using one or more
methods within the same group, they are ORed.
Placing a '!' before a name means 'not'. Where {u=joeb} means if the current
user is joeb, then display the menu item; {u=!joeb} means display the item
only if the current user is NOT joeb.
The biggest rule that you must remember about the rights methods are that
within each set of braces {}, the answer must be true. So if you use more
than one set of braces for a menu item, they all must be true. For example:
;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad,,, ...
... {d=f:\apps\wp}{u=joe,jim;n=fa164505}{s=!server2}
;─────
will only show if the user can 'see' directory F\APPS\WP _AND_ the user is JOE
_OR_ JIM _OR_ the node address is FA164505 _AND_ the user is not on SERVER2.
MENU ICONS
══════════════════════════════════════════════════════════════════════════════
WOmenu allows you to place icons on your users' menu system. This done while
either inserting or editing a menu item.
Near the icon picture box are three small buttons:
Org: Original icon - The icon in force for the menu item before editing, if
any. This is available in case you decide to go back to your original
icon but still want to save other changes to the menu item.
Def: Default icon - WOmenu has two default icons, one for sub-menus and one
for program items.
Pgm: Progrm icon - If pressed, WOmenu will attempt to extract the first icon
from the file name in the Program name text box. If this program name
has an extension, and is in the path or the full path name is given, and
the file indeed has an icon, then WOmenu will find it.
You may also use the icon comand button to pick an icon file or program
containing icons. In this case, if there is more than one icon in the file,
you will then be able to browse all of them with the up/down slider bar tool.
When you press OK, whatever icon is shown in the icon picture box will be
selected as the item's icon.
USERS WINDOWS ENVIRONMENT
══════════════════════════════════════════════════════════════════════════════
The WOmenu system can make your users' Windows environment a simple one that
is very easy to maintain. We'll explain our setup as an example.
o We set up Windows as a network install in F:\WINDOWS. We ran one user
SETUP from the Windows directory to get the default WIN.INI and
SYSTEM.INI files. We changed the shell defined in SYSTEM.INI to
WOMENU.EXE. Then we copied the necessary files to our own SETUP
directory under F:\WINDOWS. These files, surprisingly enough, consisted
of only the following files:
WIN.COM
WIN.INI
SYSTEM.INI
Note that no Program Manager files are needed at all. If you want your
users to have a screen saver, a particular screen background, etc., then
set it up for this test user before copying these files to each user's
Windows directory.
o For each DOS program our users may run through their menu definitions, we
defined a PIF file. Our defined items in the INI (menu) file point to
these PIF files on the Pgm#= lines.
o To set up a user, we add them to a WINDOWS group in Syscon, make a
directory under their private directory called WINDOWS, and copy the
above listed files into that directory.
o Our users run mostly DOS PIF-defined programs and have no need for a
mouse. WOmenu runs and handles nicely without one.
o Consider removing the Task Manager function from your users' Windows
setup so that the Ctrl-Esc key will not confuse them (or render the Out
message function less effective).
That's all there is to it. It's easy and quick to add/delete users from the
menu setup. And we have security while providing our users with true task
switching.
DOS ENVIRONMENT VARIABLES
══════════════════════════════════════════════════════════════════════════════
WOmenu can use up to three DOS variables to tell the system about your
environment; user ID, server name and workstation node address.
In the case of NetWare, you probably do not need to define these rights.
However, to do so, define and load this DOS variable once during the main
login script with the correct information. This is, of course exactly what
you want on non-NetWare environments. The NetWare syntax is:
DOS SET USERID="%LOGIN_NAME"
where userid can be called anything you wish. You could then add this name
to various rights as desired. Womenu takes care of the rest.
If you plan on using server name rights, then you would set up the server name
variable in a similar manner. The NetWare syntax (although probably not
needed) is,
DOS SET SERVER="%FILE_SERVER"
place the above line in the users login script.
The node address variable is needed if you intend to restrict any menu items
by comparing a work station's node address. The NetWare syntax (although
probably not needed) is:
DOS SET _NODE="%P_STATION"<<4
where the <<4 takes the first 4 numbers away from the actual twelve digit
address.
DOS PROGRAM PIF FILES
══════════════════════════════════════════════════════════════════════════════
When placing DOS programs on a user's menu system, there are a few cautions
and guidelines we have learned and would like to pass on to you. they are all
optional but make a lot of sense toward keeping the menu usable and secure.
o Make sure the entry for the "Window Title" is the same as the entry you
will enter for the item while in Setup Mode. In this way, WOmenu will
easily be able to find this program's DOS window when trying to determine
if the user has already run the program once or not. (WOmenu attempts to
allow users only one run of each program on their menu.)
o Recommend setting the option "Full Screen" to on.
o Recommend setting the option "Background" to on.
o Recommend locking out all "Shortcut Keys" except Alt-Tab (which is needed
to switch between programs and back to the menu window).
SOFTWARE METERING SERVICE
══════════════════════════════════════════════════════════════════════════════
WOmenu includes a powerful capability called software metering which enables
you to control the number of simultaneous run instances of an application.
For instance, if you have bought 25 licenses for Microsoft Word, you now have
the means to insure that only 25 copies are run at one time from with the menu
system on your network.
There are more expensive and perhaps more foolproof offerings on the market
for this service, but WOmenu does the job simply and easily. And we believe
that an administrator's effort level in attempting to control software
licensing is at least 95% of any large distributor's concerns.
Here is how you set up metering:
1. Fill in these commands for the WOMENU.INI file with the Setup command:
Metering: checked
File: f:\share\womenu.mtr (or something like that)
Users must have WRITE and ERASE rights to the above area.
2. Place the meter right on those commands you want metered, for example:
;─────
Pgm1=&Word, MICROSOFT WORD, Windows word processing, ...
... f:\apps\word\winword.exe, h:\,,, {m=word:25}
;─────
will meter the use of F:\APPS\WORD\WINWORD.EXE for all accesses from WOmenu.
Simply add this right to the menu item with the Edit command. If 25 instances
are already in use (in this example), then WOmenu will instruct the user that
the maximum licenses are in use and to try again later.
The syntax is important. The application keyword, in this case WORD, may be
10 or less characters with no spaces, followed by an immediate colon ':',
followed by an immediate number from 1 to 999 (with no spaces) -or- if no
:number is entered, then 999 is assumed (good for counting accesses only).
These both work:
{m=word:25} ;limit 25
{m=word} ;no limit
Of course anyone accessing WINWORD.EXE from outside of the menu system will
not be metered in this way. See the WOMETER METERING UTILITY section to find
out how to meter DOS software runs from outside the menu system. Also, if you
call the application from more than one menu item in your menu file, make sure
you place the same meter rights for each item.
Note: RECOMMEND DELETING THE METER FILE PERIODICALLY/NIGHTLY...
If any user locks up while in a metered application, or gets rebooted at that
point, then the meter count for that app will remain off by one (it will show
one greater than actual). For this reason, we recommend deleting the defined
meter file periodically, perhaps at night before or after your backup. See
WOMETER WINDOWS METERING UTILITY section for how to do this automatically.
Be careful when viewing your meter file. The recommended way to view it is
with WOmeter (see below).
WOMETER WINDOWS METERING UTILITY
══════════════════════════════════════════════════════════════════════════════
This utility can optionally monitor your software usage from outside of the
menu system but from within Windows. All of your users' programs can be
reliably monitored for metering.
There are no command line parameters; just run:
WOMETER
WOMETER.EXE will attempt to find the meter file's name in its WOMETER.INI
file. If it does not, it will make this file in its home directory and then
you can fill in the name of the meter file, like:
[Setup]
Meter File=c:\windows\womenu.mtr (or something like that)
WOmeter allows real-time reseting of specific metered applications, in case
the count has gone astray (perhaps from user lockups, etc.).
You may also set up WOmeter to automatically erase your meter file on a daily
basis at a specified time. The default is 00:01 (one minute after midnight).
You may also define the length of time WOmeter waits between re-reads of the
meter file (between 10 and 60 seconds).
If you also use our DOS-based menu product, DOSmenu, WOmenu can easily work
in concert with it for both meter files and log files. Simply point the name
and location of these files to the same files delineated in the DOSmenu INI
file. Then you will have a complete picture of your user activities on your
network.
DOSMENU MENU SYSTEM
══════════════════════════════════════════════════════════════════════════════
We have another product called DOSmenu that is a network menuing system as
well. However, DOSmenu works from DOS. It is a very popular product that
can work nicely in conjunction with WOmenu. If you are interested in this
product, please contact us. If you wish to try it first, it is available on
the Internet via anonymous ftp and the World Wide Web, in shareware form.
See the cover page of this manual.
SHAREWARE
══════════════════════════════════════════════════════════════════════════════
Evaluation Copy
───────────────
THIS IS NOT FREE SOFTWARE! You may evaluate and use this product, but if you
decide to make use of it on a regular basis, you must register your copy.
Note: Businesses, government agencies and institutions are required to
register this software package before extended use.
We offer several inducements to you for registering. First of all, you will
receive the most up-to-date copy of the program -- and we update the program
on a regular basis. Second, we have additional mini-utilities that work
nicely with WOmenu not included in this package that we will ship to you upon
registration. Third, you will never see the shareware message again. Make no
mistake, however -- this is a fully functional version of WOmenu that is not
"crippled" in any way.
Distribution
────────────
This is "user-supported" software. You are hereby granted permission to
distribute this evaluation copy of WOmenu and its documentation, subject to
the following conditions:
1. Shareware WOmenu may be distributed freely without charge in evaluation
form only. The original PKZIP file, WOMENU??.ZIP, is preferred.
2. WOmenu in its shareware form may not be sold, licensed, or a fee charged
for its use. If a fee is charged in connection with WOmenu, it must cover
the cost of copying or dissemination only. Such charges must be clearly
identified as such by the originating party. Under no circumstances may
the purchaser be given the impression that he is buying a registered
version of WOmenu.
3. Shareware WOmenu must be presented as a complete unit with documentation.
Neither WOmenu nor its documentation may be amended or altered in any way
without permission of the copyright holder.
4. By granting you the right to distribute the evaluation form of WOmenu, you
do not become the owner of WOmenu in any form.
Any other use, distribution or representation of WOmenu is expressly forbidden
without written consent from the copyright holder.
Registration
────────────
The non-commercial single-user registration fee for WOmenu is $45.00 US plus
$10 S/H.
The commercial/government and multi-system site fee for WOmenu is:
Network environments:
Per server - $195 US plus $10 S/H.
Non-network environments:
Per machine - $45 US plus $10 S/H.
Send a check, money order or company P.O. for the appropriate amount to:
Bremer Corporation
5114 Balcones Woods Drive
Suite 307-372
Austin, Texas 78759
We also accept Mastercard, Visa, American Express and Corporate American
Express card telephone orders.
Thank you.
24-Hr Telephone: 512-328-2465 INTERNET email: zboray@io.com
CompuServe Email: 71614,2556
See WOORDER.DOC for a ready-made ordering form.
Disclaimer
──────────
The author does not warrant that the functions contained in this program will
meet your requirements or that the program operation will be uninterrupted or
error free.
The author specifically disclaims all other warranties, expressed or implied,
including but not limited to implied warranties of fitness for any particular
purpose and of merchantability.
In no event will the author be liable to you for any damages, including but
not limited to any lost profits, lost savings, commercial damage or other
incidental or consequential damages arising out of the use or inability to use
this program, or for any claim by any other party.
Trademarks
──────────
Trademarks of companies or products mentioned in WOmenu documentation files
are the property of their respective companies.